Verify each finding against the current code and only fix it if needed.

Inline comments:
In
`@source/administration-guide/configure/authentication-configuration-settings.rst`:
- Around line 1930-1936: The document incorrectly says a setting "can only be
set in config.json" while the table lists an environment variable (e.g., the
GitLabSettings > Scope row); update the wording in the affected blocks to
accurately reflect both options (e.g., "This setting can be set in config.json
or via the corresponding environment variable") and apply the same change to the
other occurrences referenced (the blocks around lines 2053-2059 and 2204-2210)
so the System Console / config.json vs environment variable guidance is
consistent.
- Around line 1723-1724: Update the two SAML scoping configjson keys to use the
same prefix as other SAML settings: change the bare keys ScopingIDPProviderId
and ScopingIDPName to .SamlSettings.ScopingIDPProviderId and
.SamlSettings.ScopingIDPName respectively so the :configjson: entries align with
the rest of the page’s naming convention.

In `@source/administration-guide/configure/compliance-configuration-settings.rst`:
- Around line 374-377: The documentation is inconsistent: the paragraph claims
exports are written to the "exports" subdirectory but the example config shows
"FileLocation": "export"; update one to match the other. Locate the text that
mentions the default directory ("exports" subdirectory) and the config example
showing "FileLocation": "export" and make them consistent (either change the
config example to "FileLocation": "exports" or change the paragraph to refer to
"export"), ensuring the displayed config value and the prose use the exact same
string.

In
`@source/administration-guide/configure/environment-configuration-settings.rst`:
- Around line 4319-4324: The paragraph stating the setting "can be set via mmctl
or changed in the database" contradicts the table that lists config.json and the
environment variable MM_JOBSETTINGS_CLEANUPCONFIGTHRESHOLDDAYS; pick one
authoritative management path and update the text so all references to
CleanupConfigThresholdDays (and MM_JOBSETTINGS_CLEANUPCONFIGTHRESHOLDDAYS) are
consistent—for example, change the sentence to state that the setting is only
configurable in the database (and via mmctl) and remove the config.json/env var
entries from the table, or vice versa, ensure the System Console line remains
N/A and adjust the other lines to match the chosen source of truth (config.json,
env var, or mmctl/database).
- Around line 4451-4452: The sentence in the resolver explanation contains a
grammar error: change "Mattermost resolve using the local resolver" to
"Mattermost resolves using the local resolver" (i.e., replace the phrase
"Mattermost resolve" with "Mattermost resolves") in the sentence that reads "If
that fails, Mattermost resolve using the local resolver (by reading the
``/etc/hosts`` file first), then checking for matching CIDR rules." Keep the
rest of the sentence and punctuation intact.
- Around line 1950-1952: The "config.json-only settings" subsection uses a '^'
underline which is inconsistent with adjacent subsections that use '~'; update
the RST heading underline for "config.json-only settings" to use the same '~'
character (and matching length) so the heading depth matches its peers and the
page's heading hierarchy remains sequential and consistent.
- Around line 2558-2560: The paragraph mixes units and double-applies the "* 24"
factor; update the wording to use consistent units and a clear formula: state
that MaxImageResolution is expressed in megabytes (MB), that each decoded image
uses approximately "MaxImageResolution * 24" megabytes, and that total
worst-case memory ≈ MaxImageResolution * MaxImageDecoderConcurrency * 24 (in
MB). Replace the ambiguous sentence "MaxImageResolution * 24 bytes" with this
clarified unit-aware formula, and keep the example using MaxImageResolution and
MaxImageDecoderConcurrency (e.g., 33 * 4 * 24 = 3168MB) so readers can perform
correct capacity planning; reference the MaxImageResolution and
MaxImageDecoderConcurrency settings when making the change.
- Around line 1955-1971: The :configjson: entries for the post- and file-search
settings use bare keys but should use full config.json paths; update the
:configjson: value for the enable-post-search block from "EnablePostSearch" to
"ServiceSettings.EnablePostSearch" and likewise update the enable-file-search
block's :configjson: from "EnableFileSearch" to
"ServiceSettings.EnableFileSearch" so they match the Mattermost config.json
structure and the page's existing pattern.

In
`@source/administration-guide/configure/experimental-configuration-settings.rst`:
- Around line 831-842: The new config setting directive
advanced-logging-selfhosted is present but lacks its full documentation section;
add a complete section under that directive that includes a clear section title
(e.g., "Advanced Logging — Self‑Hosted"), a prose description of behavior and
capability boundaries, and a config table showing relevant JSON keys, types,
default values, and example snippets for AdvancedLoggingJSON; update or add
notes about UI/Console availability (System Console: Experimental > Features)
and any environment restrictions so admins understand how to configure the
self-hosted variant, referencing the existing advanced-logging-selfhosted
directive and AdvancedLoggingJSON symbol to locate where to insert the content.
- Around line 627-651: Add the missing Sphinx metadata blocks for the two new
settings by inserting a ".. config:setting::" directive above each setting
section: one for "ExperimentalSettings.DisableAppBar" (the Disable app bar
section) and one for "ExperimentalSettings.ExperimentalViewArchivedChannels"
(the View archived channels section); ensure you follow the same local
style/format used elsewhere on the page (same indentation, inline code
formatting of the setting name, and options text) so the settings become
discoverable and indexable like the other documented config entries.

In `@source/administration-guide/configure/plugins-configuration-settings.rst`:
- Around line 2147-2165: The documentation duplicates/conflicts the availability
of the EnableUploads config key: the new "Enable plugin uploads" section claims
EnableUploads is config.json-only while an earlier "Upload Plugin" entry
documents a System Console path and environment variable for the same key;
reconcile them by either merging the two entries into a single authoritative
entry for the EnableUploads setting (keeping consistent metadata like
:configjson:, :systemconsole:, :environment: and the displayname) or explicitly
mark the new section as not config.json-only and update its metadata to match
the earlier "Upload Plugin" documentation so there is one source of truth for
EnableUploads.
- Around line 2153-2161: Replace the inconsistent UI label "Plugins >
Management" with the canonical product label "Plugins > Plugin Management"
wherever it appears in the "Enable plugin uploads" section (the block under the
"Enable plugin uploads" heading and the earlier bullet point), ensuring both
occurrences of the literal string "Plugins > Management" are updated to "Plugins
> Plugin Management" to match Mattermost's standard UI terminology.
- Around line 2167-2185: Add a warning admonition under the "Allow insecure
download URL" section to call out the supply-chain/security risk of enabling
insecure remote plugin downloads: reference the setting/section name
(allow-insecure-download-url / "Allow insecure download URL") and the
config.json key ("AllowInsecureDownloadUrl") and insert a warning-level RST
admonition that explains this enables insecure plugin download behavior, warns
to only enable for trusted sources or temporary testing, and recommends keeping
it false in production; ensure the admonition uses the RST warning directive so
it renders as a prominent caution.

In
`@source/administration-guide/configure/push-notification-server-configuration-settings.rst`:
- Around line 150-163: Update the new push-notification-buffer block to use the
scoped config key and valid JSON: change the `:configjson:` value from the
unscoped key to the properly scoped key used in config.json (e.g., the setting
name `PushNotificationSettings.PushNotificationBuffer` or whatever scoped key
your config uses), and fix the example JSON to remove the extra trailing quote
so the example is valid JSON (e.g., `"PushNotificationBuffer": 1000` as a
numeric value). Ensure you update the `push-notification-buffer` section
references to the corrected scoped key and the corrected JSON example so the
docs match the real config structure.

In `@source/administration-guide/configure/site-configuration-settings.rst`:
- Around line 460-473: Update the docs to use the fully-qualified config.json
key instead of the root key: change the :configjson: value and all references
from AllowedThemes to TeamSettings.AllowedThemes (match the scoped key pattern
used elsewhere on the page), and update the text and example to show the full
JSON path — e.g. show "TeamSettings": {"AllowedThemes": [...] } and the example
array like ["mattermostDark", "windows10"]; ensure references to
EnableThemeSelection remain unchanged.
- Around line 884-897: The doc currently shows the unscoped key
EnableUserStatuses; update the example and prose to show the full config.json
object path by replacing/unifying the snippet and text to use
"ServiceSettings.EnableUserStatuses": true (options true/false) and mention that
the key lives under ServiceSettings in config.json so admins can set it
correctly; ensure references to EnableUserStatuses in the section and the boxed
example are changed to ServiceSettings.EnableUserStatuses.

In
`@source/administration-guide/configure/user-management-configuration-settings.rst`:
- Around line 687-692: The :configjson: metadata for the restrict-system-admin
directive is incorrect—update the directive that begins with "..
config:setting:: restrict-system-admin" by replacing ":configjson: FileEnabled"
with the actual config key ":configjson: RestrictSystemAdmin" so the metadata
matches the real configuration setting (check the directive block containing
restrict-system-admin and the :configjson: line and change its value).
- Around line 703-705: Update the documentation example for the
"RestrictSystemAdmin" config so the JSON uses a real boolean instead of a
string: change the displayed setting from `"RestrictSystemAdmin": "false"` to
`"RestrictSystemAdmin": false` (and ensure the options list refers to true and
false without quotes) so that the config.json example is valid JSON; locate and
edit the occurrence of the "RestrictSystemAdmin" example in the
user-management-configuration-settings.rst content and fix the quoted boolean.

---

Nitpick comments:
In
`@source/administration-guide/configure/authentication-configuration-settings.rst`:
- Around line 1715-1716: The SAML subsection headings are using inconsistent
marker levels compared to nearby sections (e.g., the group heading
"config.json-only settings" and the SAML group/setting headings at the new SAML
subsection); update those headings so the group heading uses the same level
marker as neighboring groups and each per-setting heading is one deeper
(sequential hierarchy) to match the local pattern—adjust the SAML group heading
and its child setting headings at the referenced locations (the "SAML" group and
its per-setting headings) to the correct RST underline/overline marker levels so
they render and scan consistently.

In `@source/administration-guide/configure/compliance-configuration-settings.rst`:
- Around line 312-317: The new two-column grid table should be rewritten to
match the page’s existing single-line config table pattern used elsewhere:
replace the grid table for the SMTPServerTimeout entry with a single-line "This
feature’s `config.json` setting is
MessageExportSettings.GlobalRelaySettings.SMTPServerTimeout (default 1800
seconds); Environment variable
MM_MESSAGEEXPORTSETTINGS_GLOBALRELAYSETTINGS_SMTPSERVERTIMEOUT" style, and do
the same for the similar entry at 352-357 so both follow the local single-line
pattern for consistency.